System and method for simplified checkout

ABSTRACT

In various embodiments, a system and method for providing simplified checkout are provided. In example embodiments, an identifier that corresponds to a payment account of a user is received at a payment provider system. Account information from the payment account of the user is retrieved from a payment data storage of the payment provider system. The account information is used in a payment transaction involving a merchant system. A payment interface having transaction fields populated with the account information retrieved from the payment account of the user is presented to the user while the user maintains a presence on a webpage of a merchant system.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/398,271, filed on Jan. 4, 2017, now U.S. Pat. No. 10,621,582, issuedon Apr. 14, 2020; which is a continuation of U.S. patent applicationSer. No. 14/085,746, filed on Nov. 20, 2013, now U.S. Pat. No.9,547,853, issued on Jan. 17, 2017; which claims the benefit of U.S.Patent Application Ser. No. 61/728,710, filed on Nov. 20, 2012; thedisclosures of which are incorporated herein by reference in theirentireties.

FIELD

The present disclosure relates generally to electronic payments, and ina specific example embodiment, to providing a simplified checkoutprocess.

BACKGROUND

Conventionally, a consumer may be required to enter a plurality ofinformation to conduct an electronic payment. The plurality ofinformation may include, for example, an account or credit card number,a billing address, a user name, and a shipping address. When using apayment provider service, the consumer may be required to create anaccount and provide one or more funding sources to fund a purchase orpayment. This can cause a delay or inconvenience before an electronicpayment (e.g., online payment) can be processed.

BRIEF DESCRIPTION OF THE DRAWINGS

Various ones of the appended drawings merely illustrate exampleembodiments of the present invention and cannot be considered aslimiting its scope.

FIG. 1 is a diagram illustrating an example environment in whichembodiments of a system for providing simplified checkout may beimplemented.

FIG. 2 is a block diagram illustrating an example embodiment of apayment provider system.

FIGS. 3A-3D are example screenshots illustrating example user interfacesproviding simplified checkout.

FIGS. 4A-4G are example screenshots illustrating example user interfacesproviding simplified checkout with payment float.

FIG. 5 is a flow diagram of an example high-level method for providingsimplified checkout.

FIG. 6 is a flow diagram of an example high-level method for providingsimplified checkout with a payment float option.

FIG. 7 is a simplified block diagram of a machine in an example form ofa computing system within which a set of instructions for causing themachine to perform any one or more of the methodologies discussed hereinmay be executed.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the present invention. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide an understanding of variousembodiments of the inventive subject matter. It will be evident,however, to those skilled in the art that embodiments of the inventivesubject matter may be practiced without these specific details. Ingeneral, well-known instruction instances, protocols, structures, andtechniques have not been shown in detail.

Example embodiments described herein provide systems and methods forproviding a simplified checkout process. In one embodiment, anidentifier interface is presented while the user maintains a presence ona webpage of the merchant system. Accordingly, the identifier interfacemay be provided via the merchant system. The identifier interface may bea pop-up interface presented over the webpage of the merchant system. Anidentifier (e.g., an email address) that corresponds to a paymentaccount of a user is received at a payment provider system. Accountinformation (e.g., address, funding source information) from the paymentaccount of the user is retrieved from a payment data storage of thepayment provider system. The account information may be used in apayment transaction involving a merchant system. A payment interfacehaving transaction fields populated with some of the account informationretrieved from the payment account of the user is presented to the userwhile the user maintains the presence on the webpage of a merchantsystem (e.g., via the merchant system). A payment confirmation triggerthat triggers the payment provider system to process the paymenttransaction is received. In some cases, a password corresponding to thepayment account is verified prior to processing the payment transaction.

By using example embodiments of the present invention, payment fieldsmay be automatically prepopulated for the user without leaving amerchant's website. As such, the user simply needs to confirm payment.Accordingly, one or more of the methodologies discussed herein mayobviate, for example, a need for accessing a payment system or fillingin fields of a payment form. This may have the technical effect ofreducing computing resources used by one or more devices within thesystem. Examples of such computing resources include, withoutlimitation, processor cycles, network traffic, memory usage, storagespace, and power consumption.

With reference to FIG. 1, a diagram illustrating an example environment100 in which embodiments of a system for providing simplified checkoutmay be implemented is shown. The environment 100 comprises a user device102 coupled via a network 104 (e.g., the Internet, wireless network,cellular network, or a Wide Area Network (WAN)) to a merchant system 106and a payment provider system 108. In example embodiments, the merchantsystem 106 is distinct from the payment provider system 108—that is, themerchant system 106 is different or separate from the payment providersystem 108. The network 104 may be implemented as a single network or acombination of a plurality of networks.

The user device 102 may be implemented using any appropriate hardwareand software configured for wired or wireless communication over thenetwork 104. Accordingly, the user device 102 may comprise a mobilephone, desktop computer, laptop computer, tablet, or any othercommunication device (e.g., mobile device) that a user may utilize toaccess and communicate via the network 104. Communications via thenetwork 104 may include search requests for goods or services(collectively referred to as “items”) that are offered for sale by amerchant via the merchant system 106, and transactions to be conductedfor an item from the merchant system 106 including payment for the item.As such, the user device 102 may be a device of a user (e.g., consumer),which is used to perform a payment transaction involving items withinthe environment 100.

The user device 102 may include one or more browser applications (notshown) which may be used, for example, to provide a convenient interfaceto permit the user to browse information available over the network 104.For example, the browser application may be implemented as a web browserconfigured to view information available over the Internet or access awebsite of the merchant system 106 or the payment provider system 108.

Additionally, the user device 102 may include one or more useridentifiers which may be implemented, for example, as operating systemregistry entries, cookies associated with the browser application,identifiers associated with hardware of the user device 102, or otherappropriate identifiers which may be used for payment, user, or deviceauthentication or identification. In one embodiment, the user identifiermay be used by the payment provider system 108 to associate the user ofthe user device 102 with a payment account maintained by the paymentprovider system 108 as described in further detail below.

The merchant system 106 may comprise one or more servers or devicesmaintained or used by the merchant (or other sellers) to list items forsale (or auction) and to facilitate processing a purchase of an item.The merchant system 106 may be hosted on dedicated or shared servermachines (not shown) that are communicatively coupled to enablecommunications between the server machines. Accordingly, the merchantsystem 106 may comprise a marketplace application 110 and a checkoutapplication 112 to enable the listing and purchase of items.

The marketplace application 110 may comprise or create a marketplacesystem where items may be offered for sale. The items may includedigital goods (e.g., currency, license rights) or physical goods. In oneembodiment, the marketplace application 110 may provide a number ofpublishing, listing, and price-setting mechanisms whereby a seller orthe merchant may list (or publish information concerning) goods orservices for sale, a buyer can express interest in or indicate a desireto purchase such goods or services, and a price can be set for atransaction pertaining to the goods or services. Accordingly, themerchant system 106 may further include a data storage 114 storinglistings, publications, or other information regarding available itemsfor purchase. In one embodiment, the user device 102 may interact withthe marketplace application 110 to view various items available forpurchase from the merchant system 106.

The checkout application 112 may facilitate a purchase by the user ofgoods or services identified by the marketplace application 110. Thecheckout application 112 may be configured to accept account or paymentinformation from or on behalf of the user through the payment providersystem 108 over the network 104. For example, the checkout application112 may transmit transaction information to the payment provider system108 (e.g., purchase request, user identifier), receive information fromthe payment provider system 108 (e.g., a transaction identifier, storeduser account information such as billing or shipping address), andreceive and process a payment confirmation from the payment providersystem 108. The checkout application 112 may also be configured toaccept one or more different funding sources for payment processing fromthe user or the payment provider system 108.

The payment provider system 108 manages payments within the environment100. In example embodiments, the payment provider system 108 maycomprise one or more servers maintained by a payment service providerthat manages payments between the user and an operator of the merchantsystem 106. In this regard, the payment provider system 108 may includeone or more payment applications which may be configured to interactwith the user device 102 and the merchant system 106 over the network104 to facilitate the purchase of goods or services by the user of theuser device 102. The payment provider system 108 will be discussed inmore detail in connection with FIG. 2 below.

It is noted that the environment 100 shown in FIG. 1 is exemplary. Forexample alternative embodiments may comprise any number of user devices102 and merchant systems 106 in the environment 100. Additionally, in analternative embodiment, some functions of the checkout application 112may be embodied within the payment provider system 108 and vice-versa.

Referring now to FIG. 2, a detailed block diagram of the paymentprovider system 108 is shown. The payment provider system 108 managesthe processing of payments for transactions between the user of the userdevice 102 and the merchant system 106. The transactions may involve thepurchase of an item offered via the merchant system 106. Accordingly,the payment provider system 108 may comprise one or more payment andtransaction applications that include a communication module 202, anaccount module 204, a data module 206, a transaction module 208, a floatmodule 210, and a payment data storage 212 all communicatively coupledtogether. The multiple components themselves are communicatively coupled(e.g., via appropriate interfaces), either directly or indirectly, toeach other and to various data sources to allow information to passbetween the components or to allow the components to share and accesscommon data. Advantageously, the components of the application(s) may beconfigured to interact with the merchant system 106 on behalf of theuser of the user device 102 during a transaction with the checkoutapplication 112 to manage payments.

The communication module 202 manages communications and exchange of datawith other systems and devices of the environment 100. Accordingly, thecommunication module 202 may receive a request (e.g., an API call) forpayment or account information of the user of the user device 102 or toprocess a payment transaction from the merchant system 106. In response,the communication module 202 may, for example, transmit instructions forcausing presentation of one or more user interfaces where paymentprocessing information may be viewable by the user.

The account module 204 manages payment accounts and authentication of auser of a payment account. Accordingly, the account module 204 receiveslogin information (e.g., email address, cookie) and may determineexistence of a payment account for the user of the user device 102 ormay create a new account if necessary. Furthermore, the account module204 may receive user credentials or login information (e.g., from theuser entering the login information with the client device 102 or themerchant system 106) and authenticate the user using the logininformation. Additionally, the login information may be obtained from acookie or other identifier from the user device 102. For example, theuser device 102 may include one or more identifiers (e.g., operatingsystem registry entries, cookies associated with the browserapplication, identifiers associated with hardware of the user device102, payment/user/device authentication or identification identifiers)that may be used by the account module 204 to associate the user withtheir payment account, and which can be used to identify, login, orauthenticate the user during a payment transaction process.

The data module 206 retrieves and provides account information from thepayment account for populating transaction fields on a payment interfacewhich may be provided on a website of the merchant system 106. In oneembodiment, the data module 206 retrieves account information from thepayment data storage 212. Each user account may have account informationassociated with the individual user. For example, the accountinformation may include private financial information of the user (e.g.,account number, credit card information, bank account information,billing address), passwords, device identifiers, user names, phonenumbers, shipping address, or other information which may be used tofacilitate online payment transactions for the user. In one embodiment,some of the account information may be provided to the merchant system106 to populate (or pre-fill in) transaction fields on the paymentinterface provided on or associated with the website of the merchantsystem 106 as will be discussed in more detail below.

The transaction module 208 may comprise a transaction processingapplication that processes payment information to complete a paymenttransaction (e.g., to obtain payment from the user and send to themerchant). Accordingly, the transaction module 208 may receiveinformation from the user device 102 or the merchant system 106 forprocessing and process the information. Furthermore, the transactionmodule 208 may store details of transactions to the payment data storage212 and associate those details to a corresponding payment account ofthe user.

The float module 210 manages floating of a payment by the paymentprovider system 108 for the user. In example embodiments, the user maybe able to make a purchase without a funding source or without providingpayment at the time of the purchase transaction. The float module 210may assess a risk to “float” payment to the user, for example, thoughaccessing one or more social networks, IP addresses, or other publicdata. If the calculated risk is low and the user is approved, thepayment provider service 108 may float the user for the purchase.Accordingly, the float module 210 (e.g., via the communication module202) may cause a user interface to provide a float option to the user.The float module 210 may then receive an indication of acceptance of thefloat option and float payment for the user. In some embodiments, thefloat module 210 may inform the user of a predetermined time period thatthe user is required to pay the floated payment back to the paymentprovider system 108. Additionally, the float module 210 may provide auser agreement indicating terms and conditions of the float option tothe user for review, and receive acknowledgement of agreement with theterms and conditions. The user is required to pay back the float amountwithin the predetermined time period (e.g., seven days). Exampleembodiments directed to floating payment will be discussed in moredetail in connection with FIG. 4 below.

FIGS. 3A-3D are example screenshots illustrating user interfacesprovided in a simplified checkout process. In accordance with oneembodiment, the user simply provides a username and password associatedwith the payment account of the user at the payment provider system 108in order to checkout (e.g., pay for purchase of an item). Referring toFIG. 3A, the user is on a website of the merchant or seller (e.g.,provided by the merchant system 106). More specifically, the user may beon a shopping cart or shopping bag page of the website after havingselected an item to purchase from the merchant or seller. The user maybe provided an option in the form of a checkout button 302 to checkoutusing a payment service (e.g., provided by the payment provider system108). Alternatively, the user may have an option to initiate paymentusing a conventional secure checkout process provided by the merchant.

Upon selection of the checkout button 302, a pop-up interface 310 may bepresented to the user as shown in FIG. 3B. The user remains on themerchant's website while the pop-up interface 310 is presented. Thepop-up interface 310 may request that the user provide identifier orlogin information, such as an email address, associated with the user'spayment account at the payment provider system 108. Other logininformation such as a user name or password may also be provided invarious embodiments. The login information may also be obtained from acookie or other identifier from the user device 102. For example, theuser device 102 may include one or more identifiers (e.g., operatingsystem registry entries, cookies associated with the browserapplication, identifiers associated with hardware of the user device102, payment/user/device authentication or identification identifiers)that may be used by the payment provider system 108 to associate theuser with their payment account, and which may be used to access, login,or authenticate the user during the payment process. If the user doesnot have a payment account with the payment provider system 108, theuser may sign up for the payment account through the pop-up interface310.

Further still, the user may sign up (or sign in) using informationassociated with a social network. For example, if the user has aFacebook® account, the user may sign up for the payment account by usinginformation that is already stored to their Facebook® account.

In one embodiment, the payment provider system 108 may have knowledge ofthe user's login information (e.g., email address) from the user device102, such as through a previous use. In this embodiment, the user mayskip having to enter the login information in the interface 310 of FIG.3B and may be taken directly to the interface shown in FIG. 3C.

Assuming the user has a payment account with the payment provider systemand has logged into their payment account (or provided enoughinformation such as an identifier of the user or the user device 102 forthe payment provider system 108 to identify the user and access thepayment account), the user may be presented with a user interface withtransaction fields populated with account information from the paymentprovider system 108 as shown in the example screenshot of FIG. 3C. Whilethe transaction fields are shown in a payment interface 322 that is apop-up screen, alternatively, the transaction fields may equally as wellbe provided on a main screen or interface of the merchant website.

The transaction fields may include, for example, a shipping address,billing address, and funding source information (e.g., default paymentmethod). In one embodiment, the shipping address and/or the fundingsource information may be partially redacted for security. In oneembodiment, the funding source information may only indicate a fundingmethod to be used, but does not provide enough financial accountinformation that would allow the merchant system 106 to process thepayment transaction. In other embodiments, more or less of the accountinformation may be shown. Additionally, while the funding sourceinformation is simply shown as “default payment method” for the paymentaccount, more detailed information may be shown (e.g., full or partialcredit card numbers). The populated account information may be edited(or replaced with new account information) by selecting an edit button320.

Once the user has verified or corrected the account information, theuser may select a payment confirmation button 324 to trigger the paymenttransaction processing (e.g., place and pay for an order of the item).In one embodiment, the user may be requested to enter a passwordcorresponding to the payment account to confirm the payment transaction.In accordance with one embodiment, the checkout application 112 may senda payment transaction request to the payment provider system 108 toprocess the payment transaction using the account or payment informationin the transactions fields. In an alternative embodiment, the merchantsystem 106 may process the payment transaction using the accountinformation in the transaction fields. In either case, the user ispresented with the user interface shown in FIG. 3D upon completion ofthe payment processing (e.g., payment is authorized) that confirmscompletion of the purchase transaction.

It is noted that the user remains on the website provided by themerchant system 106 during the payment transaction process. As such, themerchant system 106 (e.g., via the checkout application 112) mayexchange data with the payment provider system 108 to send and receivetransaction information (e.g., send identifier information to thepayment provider system 108, receive account information from thepayment provider system 108). As such, the user may transact for an item(e.g., checkout) simply by entering, for example, an email address and apassword, without having to leave the merchant's website.

FIGS. 4A-4G are example screenshots illustrating example user interfacesfor providing simplified checkout with payment float. Referring to FIG.4A, the user is on a website of the merchant or seller (e.g., providedby the merchant system 106). More specifically, the user may be on ashopping cart or shopping bag page of the website after having selectedan item to purchase from the merchant or seller, and is ready tocheckout. The user may be provided an option in the form of a checkoutbutton 402 to checkout using a payment service (e.g., provided by thepayment provider system 108). Alternatively, the user may have an optionto initiate payment using a conventional secure checkout processprovided by the merchant.

Upon selection of the checkout button 402, a pop-up interface 410 may bepresented to the user as shown in FIG. 4B. The user remains on themerchant's website while the pop-up interface 410 is presented. Thepop-up interface 410 may request that the user provide identifier orlogin information, such as an email address, associated with the user'spayment account at the payment provider system 108. Other logininformation such as user name or password may also be provided invarious embodiments. The login information may also be obtained from acookie or other identifier from the user device 102. For example, theuser device 102 may include one or more identifiers (e.g., operatingsystem registry entries, cookies associated with the browserapplication, identifiers associated with hardware of the user device102, payment/user/device authentication or identification identifiers)that may be used by the payment provider system 108 to associate theuser with their payment account, and which can be used to access, login,or authenticate the user during the payment process. If the user doesnot have a payment account with the payment provider system 108, theuser may sign up for the payment account through the pop-up interface410. Further still, the user may sign up (or sign in) using informationassociated with a social network. For example, if the user has aFacebook® account, the user may sign up for the payment account by usinginformation that is already stored to their Facebook® account.

Assuming the user has a payment account with the payment provider systemand has logged into their payment account (or provided an email addressor enough information such as an identifier of the user or the userdevice 102 for the payment provider system 108 to identify the user andaccess the payment account), the user may be presented with a userinterface 420 with transaction fields populated (or pre-filled in) withaccount information from the payment provider system 108 as shown in theexample screenshot of FIG. 4C. While the transaction fields are shown ina pop-up interface 420, alternatively, the transaction fields mayequally as well be provided on a main screen or interface of themerchant website. In the example of FIG. 4C, the pop-up interface 420 isa billing address interface where a billing address and a phone numberof the user are populated into the transaction fields. The populatedaccount information may be revised (or replaced with new accountinformation) by the user.

If the shipping address is the same as the billing address, the user maysimply select a box 422 that indicates the same address. In response,the shipping address may be populated into a shipping address userinterface as shown in FIG. 4D. Alternatively, if the shipping address isnot the same as the billing address, the user may be presented with asimilar shipping address user interface only without the fieldspopulated. The user may then enter the shipping address.

Referring now to FIG. 4E, the payment provider system 108 may offer tofloat payment to the user. In one embodiment, the payment providersystem 108 may determine whether to float the payment using socialnetwork or other publicly available information. As such, the userinterface 430 informs the user that they do not need to supply anyfunding source, and that the payment provider system 108 will pay forthe purchase with the user paying the payment provider system 108 backwithin a predetermined time period (e.g., 7 days).

If the user selects to have the payment floated by the payment providersystem 108 (e.g., by selecting a link 432), the user is presented with afurther user interface 440 that displays a user agreement for using thefloat option as shown in FIG. 4F. The user may be required to provideacknowledgement of agreement with the terms and conditions of the useragreement. In embodiments where the user would like to use the floatoption and does not have a payment account with the payment providersystem 108, the user may create the payment account by, for example,entering and confirming a password as shown in FIG. 4E.

If the user does not wish to use the float option, the user may select alink 434 in FIG. 4E to pay using a user funding source. In thisembodiment, the user may be provided a user interface 450 of FIG. 4Gwhich asks the user to enter specific information about the fundingsource (e.g., credit or debit card). The user may also create a paymentaccount with the payment provider system 108 on this user interface 450.It is further noted that, in example embodiments, the prepopulatedtransaction process discussed in connection with FIG. 3A-3D may beutilized if the user does not wish to use the float option.

FIG. 5 is a flow diagram of an example high-level method 500 forproviding simplified checkout at a merchant website (hosted by themerchant system 106) using account information provided by the paymentprovider system 108. The method 500 is discussed from the perspective ofthe payment provider system 108.

In operation 502, a purchase request is received. In exampleembodiments, the communication module 202 may receive a request (e.g.,an API call) that initiates the payment process.

In response, the communication module 202 may, for example, causepresentation of an identifier interface (e.g., pop-up interface 310) inoperation 504. In one embodiment, the communication module 202 mayprovide the identifier interface to be displayed in association with themerchant website. In an alternative embodiment, the communication module202 may provide instructions that cause the merchant system 106 topresent the identifier interface. In a further embodiment, theidentifier interface is generated by the merchant system 108 withoutinstructions from the communication module 202, resulting in operation504 being optional or not necessary.

In operation 506, an identifier is received by the communication module202. In some embodiments, the identifier is a user name, email address,or other identifier that the user provides or enters onto the identifierinterface that is presented based on operation 504. In otherembodiments, the identifier may be an identifier linked to the userdevice 102 of the user. For example, the identifier may be an operatingsystem registry entry, a cookie associated with the browser applicationof the user device 102 or an identifier associated with hardware of theuser device 102. In the case where the identifier is that of the userdevice, operation 504 may be optional.

In operation 508, account information may be retrieved based on theidentifier received in operation 506. Accordingly, the account module204 may determine whether a payment account exists for the user. If thepayment account does exist, the data module 206 may retrieve certainaccount information from the payment account. The account informationmay include any one or more of a billing address, shipping address, andfunding source information (e.g., method of payment without providingfull financial account information).

In operation 510, the account information is used to populate a paymentinterface (e.g., payment interface 322 of FIG. 3C). In one embodiment,the payment interface is generated by the merchant system 108 withoutinstructions from the payment provider system 108. In anotherembodiment, the data module 206 or communication module 202 may providethe payment interface to the merchant system 106 to be displayed inassociation with the merchant website (e.g., as a pop-up over a merchantwebpage or in fields on the merchant webpage) and/or provideinstructions that cause the merchant system 106 to present the paymentinterface on their website.

A payment confirmation trigger is received in operation 512. In oneembodiment, the payment process confirmation may include a passwordprovided by the user to trigger the payment processing. The password maybe used by the payment provider system 108 (e.g., the account module 202or the transaction module 208) to verify or authenticate the user inorder to process the payment transaction. In example embodiments, thecommunication module 202 receives the payment confirmation trigger andforwards any account information and transaction information receivedwith the payment confirmation trigger (e.g., cost of product, shippingcharges, taxes, total purchase price) to the transaction module 208. Thetransaction module 208 may process and complete the payment transactionin operation 514. In some cases, the transaction module 208 may accessthe payment data storage 212 to obtain any further account informationneeded to complete the payment transaction (e.g., credit card accountnumber corresponding to the funding source information). Confirmation ofcompletion of the payment transaction may be provided to the user (e.g.,send a confirmation email).

While the operations of the method 500 were discussed from theperspective of the payment provider system 108, it is evident thatreciprocal operations are performed at the merchant system 106. Inalternative embodiments, some of the operations of the method 500 may beperformed by the checkout application 112 of the merchant system 106.For example, the payment provider system 108 may simply obtain theidentifier (operation 506) in order to retrieve the account information(operation 508) and provide the account information to the merchantsystem 106 (operation 510). The merchant system 106 may then process thepayment using the received account information.

FIG. 6 is a flow diagram of an example high-level method 600 forproviding simplified checkout at a merchant website (hosted by themerchant system 106) with a payment float option. The method 600 isdiscussed from the perspective of the payment provider system 108.

In operation 602, a purchase request is received. In exampleembodiments, the communication module 202 may receive a request (e.g.,an API call) that initiates the payment process.

In response, the communication module 202 may, for example, causepresentation of an identifier interface (e.g., pop-up interface 410) inoperation 604. In one embodiment, the communication module 202 mayprovide the identifier interface to be displayed in association with themerchant website. In an alternative embodiment, the communication module202 may provide instructions that cause the merchant system 106 topresent the identifier interface. In a further embodiment, theidentifier interface is generated by the merchant system 108 withoutinstructions from the communication module 202, resulting in operation604 being optional or not necessary.

In operation 606, an identifier is received by the communication module202. In some embodiments, the identifier is a user name, email address,or other identifier that the user provides or enters onto the identifierinterface that is presented based on operation 604. In otherembodiments, the identifier may be an identifier linked to the userdevice 102 of the user. For example, the identifier may be an operatingsystem registry entry, a cookie associated with the browser applicationof the user device 102, or an identifier associated with hardware of theuser device 102. In the case where the identifier is that of the userdevice, operation 604 may be optional.

In operation 608, a determination is made as to whether the user has apayment account with the payment provider system 108. The account module204 may perform the determination. If no account exists, then a paymentaccount may be created for the user in operation 610 if the user wishesto create the payment account.

Once the payment account is created or if the payment account alreadyexists for the user, then in operation 612, the float module 210determines whether to float payment for the user. For example, the floatmodule 210 may assess a risk to “float” payment to the user, forexample, though accessing one or more social networks, IP addresses, orother public data. If the calculated risk is low and the user isapproved, the float module 210 may provide a float option to the user.It is noted that in some cases, the determination to float payment maybe made prior to creating a payment account for the user.

In operation 614, a determination is made as to whether the user acceptsthe float option. If the user accepts the float option, the paymentprovider system 108 may pay for the purchase and expect payment from theuser within a predetermined time period (e.g., seven days).

FIG. 7 is a block diagram illustrating components of a machine 700,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 7 shows a diagrammatic representation of the machine700 in the example form of a computer system and within whichinstructions 724 (e.g., software, a program, an application, an applet,an app, or other executable code) for causing the machine 700 to performany one or more of the methodologies discussed herein may be executed.In alternative embodiments, the machine 700 operates as a standalonedevice or may be connected (e.g., networked) to other machines. In anetworked deployment, the machine 700 may operate in the capacity of aserver machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 700 may be a server computer, a clientcomputer, a personal computer (PC), a tablet computer, a laptopcomputer, a netbook, a set-top box (STB), a personal digital assistant(PDA), a cellular telephone, a smartphone, a web appliance, a networkrouter, a network switch, a network bridge, or any machine capable ofexecuting the instructions 724, sequentially or otherwise, that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude a collection of machines that individually or jointly executethe instructions 724 to perform any one or more of the methodologiesdiscussed herein.

The machine 700 includes a processor 702 (e.g., a central processingunit (CPU), a graphics processing unit (GPU), a digital signal processor(DSP), an application specific integrated circuit (ASIC), aradio-frequency integrated circuit (RFIC), or any suitable combinationthereof), a main memory 704, and a static memory 706, which areconfigured to communicate with each other via a bus 708. The machine 700may further include a graphics display 710 (e.g., a plasma display panel(PDP), a light emitting diode (LED) display, a liquid crystal display(LCD), a projector, or a cathode ray tube (CRT)). The machine 700 mayalso include an alpha-numeric input device 712 (e.g., a keyboard), acursor control device 714 (e.g., a mouse, a touchpad, a trackball, ajoystick, a motion sensor, or other pointing instrument), a storage unit716, a signal generation device 718 (e.g., a speaker), and a networkinterface device 720.

The storage unit 716 includes a machine-readable medium 722 on which isstored the instructions 724 embodying any one or more of themethodologies or functions described herein. The instructions 724 mayalso reside, completely or at least partially, within the main memory704, within the processor 702 (e.g., within the processor's cachememory), or both, during execution thereof by the machine 700.Accordingly, the main memory 704 and the processor 702 may be consideredas machine-readable media. The instructions 724 may be transmitted orreceived over a network 726 via the network interface device 720.

As used herein, the term “memory” refers to a machine-readable mediumable to store data temporarily or permanently and may be taken toinclude, but not be limited to, random-access memory (RAM), read-onlymemory (ROM), buffer memory, flash memory, and cache memory. While themachine-readable medium 722 is shown in an example embodiment to be asingle medium, the term “machine-readable medium” should be taken toinclude a single medium or multiple media (e.g., a centralized ordistributed database, or associated caches and servers) able to storeinstructions. The term “machine-readable medium” shall also be taken toinclude any medium, or combination of multiple media, that is capable ofstoring instructions for execution by a machine (e.g., machine 700),such that the instructions, when executed by one or more processors ofthe machine (e.g., processor 702), cause the machine to perform any oneor more of the methodologies described herein. Accordingly, a“machine-readable medium” refers to a single storage apparatus ordevice, as well as “cloud-based” storage systems or storage networksthat include multiple storage apparatus or devices. The term“machine-readable medium” shall accordingly be taken to include, but notbe limited to, one or more data repositories in the form of asolid-state memory, an optical medium, a magnetic medium, or anysuitable combination thereof.

Furthermore, the tangible machine-readable medium is non-transitory inthat it does not embody a propagating signal. However, labeling thetangible machine-readable medium as “non-transitory” should not beconstrued to mean that the medium is incapable of movement—the mediumshould be considered as being transportable from one physical locationto another. Additionally, since the machine-readable medium is tangible,the medium may be considered to be a machine-readable device.

The instructions 724 may further be transmitted or received over acommunications network 726 using a transmission medium via the networkinterface device 720 and utilizing any one of a number of well-knowntransfer protocols (e.g., HTTP). Examples of communication networksinclude a local area network (LAN), a wide area network (WAN), theInternet, mobile telephone networks, POTS networks, and wireless datanetworks (e.g., WiFi and WiMAX networks). The term “transmission medium”shall be taken to include any intangible medium that is capable ofstoring, encoding, or carrying instructions for execution by themachine, and includes digital or analog communications signals or otherintangible medium to facilitate communication of such software.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., code embodied on a machine-readable medium or ina transmission signal) or hardware modules. A “hardware module” is atangible unit capable of performing certain operations and may beconfigured or arranged in a certain physical manner. In various exampleembodiments, one or more computer systems (e.g., a standalone computersystem, a client computer system, or a server computer system) or one ormore hardware modules of a computer system (e.g., a processor or a groupof processors) may be configured by software (e.g., an application orapplication portion) as a hardware module that operates to performcertain operations as described herein.

In some embodiments, a hardware module may be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware module may include dedicated circuitry or logic that ispermanently configured to perform certain operations. For example, ahardware module may be a special-purpose processor, such as a fieldprogrammable gate array (FPGA) or an ASIC. A hardware module may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. For example, a hardwaremodule may include software encompassed within a general-purposeprocessor or other programmable processor. It will be appreciated thatthe decision to implement a hardware module mechanically, in dedicatedand permanently configured circuitry, or in temporarily configuredcircuitry (e.g., configured by software) may be driven by cost and timeconsiderations.

Accordingly, the phrase “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired), or temporarilyconfigured (e.g., programmed) to operate in a certain manner or toperform certain operations described herein. As used herein,“hardware-implemented module” refers to a hardware module. Consideringembodiments in which hardware modules are temporarily configured (e.g.,programmed), each of the hardware modules need not be configured orinstantiated at any one instance in time. For example, where a hardwaremodule comprises a general-purpose processor configured by software tobecome a special-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware modules) at different times. Software mayaccordingly configure a processor, for example, to constitute aparticular hardware module at one instance of time and to constitute adifferent hardware module at a different instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multiplehardware modules exist contemporaneously, communications may be achievedthrough signal transmission (e.g., over appropriate circuits and buses)between or among two or more of the hardware modules. In embodiments inwhich multiple hardware modules are configured or instantiated atdifferent times, communications between such hardware modules may beachieved, for example, through the storage and retrieval of informationin memory structures to which the multiple hardware modules have access.For example, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices, and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions describedherein. As used herein, “processor-implemented module” refers to ahardware module implemented using one or more processors.

Similarly, the methods described herein may be at least partiallyprocessor-implemented, a processor being an example of hardware. Forexample, at least some of the operations of a method may be performed byone or more processors or processor-implemented modules. Moreover, theone or more processors may also operate to support performance of therelevant operations in a “cloud computing” environment or as a “softwareas a service” (SaaS). For example, at least some of the operations maybe performed by a group of computers (as examples of machines includingprocessors), with these operations being accessible via a network (e.g.,the Internet) and via one or more appropriate interfaces (e.g., anapplication program interface (API)).

The performance of certain of the operations may be distributed amongthe one or more processors, not only residing within a single machine,but deployed across a number of machines. In some example embodiments,the one or more processors or processor-implemented modules may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In other exampleembodiments, the one or more processors or processor-implemented modulesmay be distributed across a number of geographic locations.

Although an overview of the inventive subject matter has been describedwith reference to specific example embodiments, various modificationsand changes may be made to these embodiments without departing from thebroader spirit and scope of embodiments of the present invention. Suchembodiments of the inventive subject matter may be referred to herein,individually or collectively, by the term “invention” merely forconvenience and without intending to voluntarily limit the scope of thisapplication to any single invention or inventive concept if more thanone is, in fact, disclosed.

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, plural instances may be provided forresources, operations, or structures described herein as a singleinstance. Additionally, boundaries between various resources,operations, modules, engines, and data stores are somewhat arbitrary,and particular operations are illustrated in a context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within a scope of various embodiments of thepresent invention. In general, structures and functionality presented asseparate resources in the example configurations may be implemented as acombined structure or resource. Similarly, structures and functionalitypresented as a single resource may be implemented as separate resources.These and other variations, modifications, additions, and improvementsfall within a scope of embodiments of the present invention asrepresented by the appended claims. The specification and drawings are,accordingly, to be regarded in an illustrative rather than a restrictivesense.

1. (canceled)
 2. A system, comprising: a non-transitory memorycomprising instructions; and one or more hardware processors coupled tothe non-transitory memory and configured to read the instructions tocause the system to perform operations comprising: transmitting, by auser device to a payment provider system, an identifier associatedcorresponding to a user of the user device, the identifier to beassociated with a payment account of the user at the payment providersystem; displaying, at a user device, a user interface of a merchantwebsite based on the user accessing the merchant website hosted by amerchant system, wherein the merchant system is different than thepayment provider system; in response to the user selecting an option tocheckout on the user interface of the merchant website and whilecontinuing to display the user interface of the merchant website,transmitting the identifier to the merchant system to cause the merchantsystem to communicate with the payment provider system to verify theuser; receiving, from the merchant system, instructions to display anidentifier interface corresponding to the payment account of the userbased on the user being verified by the payment provider system; and inresponse to receiving the instructions to display the identifierinterface, displaying the identifier interface while continuing todisplay the user interface of the merchant website, wherein theidentifier interface includes information corresponding to the paymentaccount of the user.
 3. The system of claim 2, wherein the informationcorresponding to the account of the user displayed in the identifierinterface is displayed in editable fields of the identifier interface.4. The system of claim 2, the operations further comprising: detectingthe selection of a payment confirmation interface element located in theidentifier interface; and in response to the detecting the selection,causing the payment provider system to process a payment.
 5. The systemof claim 2, wherein the information corresponding to the payment accountof the user includes a funding source information and an addressretrieved from a data storage of the payment provider system.
 6. Thesystem of claim 2, wherein identifier interface is a pop-up interfacedisplayed over the user interface of the merchant website.
 7. The systemof claim 2, wherein the identifier is a cookie or an identifiercorresponding to a hardware of the user device.
 8. The system of claim2, wherein the identifier is a login credential or an email address. 9.A non-transitory machine-readable medium having stored thereonmachine-readable instructions executable to cause a machine to performoperations comprising: transmitting, by a user device to a paymentprovider system, an identifier associated corresponding to a user of theuser device, the identifier to be associated with a payment account ofthe user at the payment provider system; displaying, at a user device, auser interface of a merchant website based on the user accessing themerchant website hosted by a merchant system, wherein the merchantsystem is different than the payment provider system; in response to theuser selecting an option to checkout on the user interface of themerchant website and while continuing to display the user interface ofthe merchant website, transmitting the identifier to the merchant systemto cause the merchant system to communicate with the payment providersystem to verify the user; receiving, from the merchant system,instructions to display an identifier interface corresponding to thepayment account of the user based on the user being verified by thepayment provider system; and in response to receiving the instructionsto display the identifier interface, displaying the identifier interfacewhile continuing to display the user interface of the merchant website,wherein the identifier interface includes information corresponding tothe payment account of the user.
 10. The non-transitory machine-readablemedium of claim 9, wherein the information corresponding to the accountof the user displayed in the identifier interface is displayed ineditable fields of the identifier interface.
 11. The non-transitorymachine-readable medium of claim 9, the operations further comprising:detecting the selection of a payment confirmation interface elementlocated in the identifier interface; and in response to the detectingthe selection, causing the payment provider system to process a payment.12. The non-transitory machine-readable medium of claim 9, wherein theinformation corresponding to the payment account of the user includes afunding source information and an address retrieved from a data storageof the payment provider system.
 13. The non-transitory machine-readablemedium of claim 9, wherein identifier interface is a pop-up interfacedisplayed over the user interface of the merchant website.
 14. Thenon-transitory machine-readable medium of claim 9, wherein theidentifier is a cookie or an identifier corresponding to a hardware ofthe user device.
 15. A method, comprising: transmitting, by a userdevice to a payment provider system, an identifier associatedcorresponding to a user of the user device, the identifier to beassociated with a payment account of the user at the payment providersystem; displaying, at a user device, a user interface of a merchantwebsite based on the user accessing the merchant website hosted by amerchant system, wherein the merchant system is different than thepayment provider system; in response to the user selecting an option tocheckout on the user interface of the merchant website and whilecontinuing to display the user interface of the merchant website,transmitting the identifier to the merchant system to cause the merchantsystem to communicate with the payment provider system to verify theuser; receiving, from the merchant system, instructions to display anidentifier interface corresponding to the payment account of the userbased on the user being verified by the payment provider system; and inresponse to receiving the instructions to display the identifierinterface, displaying the identifier interface while continuing todisplay the user interface of the merchant website, wherein theidentifier interface includes information corresponding to the paymentaccount of the user.
 16. The method of claim 15, wherein the informationcorresponding to the account of the user displayed in the identifierinterface is displayed in editable fields of the identifier interface.17. The method of claim 15, further comprising: detecting the selectionof a payment confirmation interface element located in the identifierinterface; and in response to the detecting the selection, causing thepayment provider system to process a payment.
 18. The method of claim15, wherein the information corresponding to the payment account of theuser includes a funding source information and an address retrieved froma data storage of the payment provider system.
 19. The method of claim15, wherein identifier interface is a pop-up interface displayed overthe user interface of the merchant website.
 20. The method of claim 15,wherein the identifier is a cookie or an identifier corresponding to ahardware of the user device.
 21. The method of claim 15, wherein theidentifier is a login credential or an email address.